Skip to content

[Merged by Bors] - Ensure protoc is installed for release CI#3621

Closed
michaelsproul wants to merge 5 commits intosigp:unstablefrom
michaelsproul:protoc-for-release
Closed

[Merged by Bors] - Ensure protoc is installed for release CI#3621
michaelsproul wants to merge 5 commits intosigp:unstablefrom
michaelsproul:protoc-for-release

Conversation

@michaelsproul
Copy link
Copy Markdown
Member

@michaelsproul michaelsproul commented Sep 30, 2022

Issue Addressed

The release CI is currently broken due to the addition of the protoc dependency. Here's a failure of the release flow running on my fork: https://github.com/michaelsproul/lighthouse/actions/runs/3155541478/jobs/5134317334

Proposed Changes

@michaelsproul michaelsproul added the work-in-progress PR is a work-in-progress label Sep 30, 2022
@michaelsproul michaelsproul changed the title Install protoc for Win/Mac release flow Ensure protoc installed for release CI Sep 30, 2022
@michaelsproul michaelsproul changed the title Ensure protoc installed for release CI Ensure protoc is installed for release CI Sep 30, 2022
@michaelsproul michaelsproul added ready-for-review The code is ready for review and removed work-in-progress PR is a work-in-progress labels Sep 30, 2022
@michaelsproul
Copy link
Copy Markdown
Member Author

This is ready for review.

Here's a run mostly working on my fork:

@michaelsproul michaelsproul added work-in-progress PR is a work-in-progress and removed ready-for-review The code is ready for review labels Sep 30, 2022
@michaelsproul
Copy link
Copy Markdown
Member Author

Actually, lcli is still broken. Will fix.

@michaelsproul michaelsproul added ready-for-review The code is ready for review v3.2.0 Minor release following v3.1.2 and removed work-in-progress PR is a work-in-progress labels Sep 30, 2022
@michaelsproul
Copy link
Copy Markdown
Member Author

@michaelsproul michaelsproul added the low-hanging-fruit Easy to resolve, get it before someone else does! label Oct 3, 2022
Copy link
Copy Markdown
Member

@paulhauner paulhauner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! The simplification of cross Dockerfiles is tidy ☺️

@michaelsproul michaelsproul added ready-for-merge This PR is ready to merge. and removed ready-for-review The code is ready for review labels Oct 3, 2022
@michaelsproul
Copy link
Copy Markdown
Member Author

Thanks!

bors r+

bors bot pushed a commit that referenced this pull request Oct 3, 2022
## Issue Addressed

The release CI is currently broken due to the addition of the `protoc` dependency. Here's a failure of the release flow running on my fork: https://github.com/michaelsproul/lighthouse/actions/runs/3155541478/jobs/5134317334

## Proposed Changes

- Install `protoc` on Windows and Mac so that it's available for `cargo install`.
- Install an x86_64 binary in the Cross image for the aarch64 platform: we need a binary that runs on the host, _not_ on the target.
- Fix `macos` local testnet CI by using the Github API key to dodge rate limiting (this issue: actions/runner-images#602).
@bors bors bot changed the title Ensure protoc is installed for release CI [Merged by Bors] - Ensure protoc is installed for release CI Oct 4, 2022
@bors bors bot closed this Oct 4, 2022
@michaelsproul michaelsproul deleted the protoc-for-release branch October 4, 2022 01:47
bors bot pushed a commit that referenced this pull request Nov 13, 2022
## Issue Addressed

Closes #3656

## Proposed Changes

* Replace `set-output` by `$GITHUB_OUTPUT` usage
* Avoid rate-limits when installing `protoc` by making authenticated requests (continuation of #3621)
* Upgrade all Ubuntu 18.04 usage to 22.04 (18.04 is end of life)
* Upgrade macOS-latest to explicit macOS-12 to silence warning
* Use `actions/checkout@v3` and `actions/cache@v3` to avoid deprecated NodeJS v12

## Additional Info

Can't silence the NodeJS warnings entirely due to #3705. Can fix that in future.
macladson pushed a commit to macladson/lighthouse that referenced this pull request Jan 5, 2023
## Issue Addressed

Closes sigp#3656

## Proposed Changes

* Replace `set-output` by `$GITHUB_OUTPUT` usage
* Avoid rate-limits when installing `protoc` by making authenticated requests (continuation of sigp#3621)
* Upgrade all Ubuntu 18.04 usage to 22.04 (18.04 is end of life)
* Upgrade macOS-latest to explicit macOS-12 to silence warning
* Use `actions/checkout@v3` and `actions/cache@v3` to avoid deprecated NodeJS v12

## Additional Info

Can't silence the NodeJS warnings entirely due to sigp#3705. Can fix that in future.
divagant-martian added a commit to divagant-martian/lighthouse that referenced this pull request Mar 14, 2023
divagant-martian added a commit to divagant-martian/lighthouse that referenced this pull request Apr 13, 2023
Woodpile37 pushed a commit to Woodpile37/lighthouse that referenced this pull request Jan 6, 2024
## Issue Addressed

The release CI is currently broken due to the addition of the `protoc` dependency. Here's a failure of the release flow running on my fork: https://github.com/michaelsproul/lighthouse/actions/runs/3155541478/jobs/5134317334

## Proposed Changes

- Install `protoc` on Windows and Mac so that it's available for `cargo install`.
- Install an x86_64 binary in the Cross image for the aarch64 platform: we need a binary that runs on the host, _not_ on the target.
- Fix `macos` local testnet CI by using the Github API key to dodge rate limiting (this issue: actions/runner-images#602).
Woodpile37 pushed a commit to Woodpile37/lighthouse that referenced this pull request Jan 6, 2024
## Issue Addressed

Closes sigp#3656

## Proposed Changes

* Replace `set-output` by `$GITHUB_OUTPUT` usage
* Avoid rate-limits when installing `protoc` by making authenticated requests (continuation of sigp#3621)
* Upgrade all Ubuntu 18.04 usage to 22.04 (18.04 is end of life)
* Upgrade macOS-latest to explicit macOS-12 to silence warning
* Use `actions/checkout@v3` and `actions/cache@v3` to avoid deprecated NodeJS v12

## Additional Info

Can't silence the NodeJS warnings entirely due to sigp#3705. Can fix that in future.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

low-hanging-fruit Easy to resolve, get it before someone else does! ready-for-merge This PR is ready to merge. v3.2.0 Minor release following v3.1.2

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants